Hey Sophie, just a tiny question.

Since you moved the git name and email to variables, should we set the current ones as default values for those workflows that are currently using the actions, or is the plan that it won't be set when using the latest and it will fail, so we need to set it up in all the projects currently using the actions?

It might be set already as default, but I couldn't see it in the PR.

Hey Sophie, just a tiny question.

Since you moved the git name and email to variables, should we set the current ones as default values for those workflows that are currently using the actions, or is the plan that it won't be set when using the latest and it will fail, so we need to set it up in all the projects currently using the actions?

It might be set already as default, but I couldn't see it in the PR.

They're only variables in the example workflows, not the actual workflows :)

When you define a workflow in a codebase you'll provide the values, for example:

jobs:
  push-code:
    name: 'Deploy: push code to Pantheon.'
    uses: thisisgain/.github/.github/workflows/03-deploy-pantheon.yml@main
    with:
      # Both of these will work:
      git_name: 'GAIN Automation'
      git_email: ${{ vars.git_email }}

These are the inputs in the workflow. From 03-deploy-pantheon.yml:

on:
  workflow_call:
    inputs:
      git_name:
        description: "The Git committer name. Can be hardcoded, or get the triggering user's name."
        type: string
        required: true
      git_email:
        description: "The Git committer email. Can be hardcoded, or get the triggering user's email."
        type: string
        required: true

It doesn't matter how you pass it in - it'll accept it either way. I'm just updating the recommendation.